Pet Feeding System

ABSTRACT

A pet feeding system for effectively communicating information between a packaged consumable product for pets and a device. The pet feeding system generally includes a container that stores a volume of a consumable product for a pet, a tag attached to the container that stores product data corresponding to the consumable product within the container, and a monitor device configured to wirelessly communicate with the tag when the tag is near the monitor device. The monitor device is configured to receive the product data from the tag and determine if the consumable product associated with the tag is acceptable for consumption by a pet using the product data. The monitor device is configured to provide an alert to the user if the consumable product associated with the tag is identified by the monitor device as having a consumption problem for the pet.

CROSS REFERENCE TO RELATED APPLICATIONS

I hereby claim benefit under Title 35, United States Code, Section119(e) of U.S. provisional patent application Ser. No. 62/336,828 filedMay 16, 2016. The 62/336,828 application is currently pending. The62/336,828 application is hereby incorporated by reference into thisapplication.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable to this application.

BACKGROUND Field

Example embodiments in general relate to a pet feeding system foreffectively communicating information between a packaged consumableproduct for pets and a device.

Related Art

Any discussion of the related art throughout the specification should inno way be considered as an admission that such related art is widelyknown or forms part of common general knowledge in the field.

Food for domesticated animals such as dogs and cats is typicallyproduced at a food manufacturing facility, and subsequently packaged anddistributed to the animal owner through various wholesale and retaildistribution channels. Food packaging typically consists of sealed bags,cans, cartons, hybrid “pop-top” containers and foil or cellophanewrapped packages. The food types may include dry kibble, wet food,frozen foods, freeze-dried or dried foods and treats. These processes,food types, food packaging containers and distribution methods are wellknown in the pet products industry.

The US Food and Drug Agency regulates pet food safety under the FederalFood, Drug and Cosmetic Act, codified as Title 21, United States Code,Chapter 9. There are three types of recalls: voluntary producer recall,recall under FDA request, or recall under FDA order under statutoryauthority.

In 2007, contaminated pet foods killed an estimated 50,000 US dogs andcats, and resulted in over $500 million in food recall, litigation anddamages costs to pet food manufacturers. The FDA stepped up its pet foodmonitoring and recall authority since the 2007 incident. Since 2008, theFDA has issues nearly 250 pet food and drug recalls. These recalls coverthousands of unique brands, and have included more than 20 millions cansof food, and well over 50 million pounds of dry food. Food recalls costmanufacturers from a few million dollars, to losses well over $50million.

Despite the frequency, economic impact and social impact of recallsassociated with pet foods, there exists no reliable method to alert petowners when the pet food is recalled, and when they should cease feedingthe food to their pet. Further, many dietary supplements andprescription medications are fed to dogs and cats. These products carrythe same risks of contamination as food. Similarly, these products aredistributed through a supply chain that has no reliable means oftracking the food to the ultimate pet consuming the item, or ofpreventing the feeding of the supplements or medications to the animal.

SUMMARY

An example embodiment is directed to a pet feeding system. One or moreof the various embodiments of the present invention manage pet foodthroughout the supply chain, from food component source acquisition toultimate consumption by pet animals. Further, one or more of the variousembodiments teaches a system and method of alerting the pet owner at themoment of feeding a recalled food or medication to the animal, andfurther provides for the monitoring of the location and volume ofconsumed and non-consumed recalled animal foods, supplements andmedications.

Therefore, one exemplary embodiment is a supply chain management systemthat minimizes a food manufacturer's liability, risk and financialexposure related to food, supplement or medication recalls.

Another exemplary embodiment is a food supply chain system and methodthat associates each manufactured food, supplement or medication productto a specific animal.

Another exemplary embodiment is a communication network providing forthe tracking of actual consumption of each food item, in real time.

Another exemplary embodiment provides for the communication betweensupplier of food, supplements or medications, and the owner of ananimal, the communication occurring at the time the owner is ready tofeed the animal.

There has thus been outlined, rather broadly, some of the embodiments ofthe pet feeding system in order that the detailed description thereofmay be better understood, and in order that the present contribution tothe art may be better appreciated. There are additional embodiments ofthe pet feeding system that will be described hereinafter and that willform the subject matter of the claims appended hereto. In this respect,before explaining at least one embodiment of the pet feeding system indetail, it is to be understood that the pet feeding system is notlimited in its application to the details of construction or to thearrangements of the components set forth in the following description orillustrated in the drawings. The pet feeding system is capable of otherembodiments and of being practiced and carried out in various ways.Also, it is to be understood that the phraseology and terminologyemployed herein are for the purpose of the description and should not beregarded as limiting.

BRIEF DESCRIPTION OF THE DRAWINGS

Example embodiments will become more fully understood from the detaileddescription given herein below and the accompanying drawings, whereinlike elements are represented by like reference characters, which aregiven by way of illustration only and thus are not limitative of theexample embodiments herein.

FIG. 1 is an exemplary diagram illustrating a devices and functions of afood tag transponder system in accordance with an example embodiment.

FIG. 2 is an exemplary diagram illustrating a devices and functions of afood tag transponder system.

FIG. 3 is an exemplary illustration of a block diagram of the devicescomprising a food tag system and method.

FIG. 4 is an exemplary illustration of a block diagram of a food bowl ona network.

FIG. 5 is an exemplary illustration of a block diagram of components ofa food container with a tag.

FIG. 6 is an exemplary diagram illustrating the process flow of a taggedfood item and food bowl on a network.

FIG. 7 is an exemplary diagram illustrating the process flow of a fooditem with a tag.

FIG. 8 is an exemplary diagram illustrating the process flow throughoutthe lifecycle of a tag.

FIG. 9 is an exemplary diagram illustrating the process of alerting apet owner.

FIG. 10 is an exemplary diagram illustrating the process of alerting apet owner.

FIG. 11A is an exemplary diagram illustrating one variation of a foodcontainer.

FIG. 11B is an exemplary diagram illustrating one variation of a foodcontainer.

FIG. 11C is an exemplary diagram illustrating one variation of a foodcontainer.

FIG. 11D is an exemplary diagram illustrating one variation of a foodcontainer.

FIG. 11E is an exemplary diagram illustrating one variation of a foodcontainer.

FIG. 11F is an exemplary diagram illustrating one variation of a foodcontainer.

FIG. 11G is an exemplary diagram illustrating one variation of a foodcontainer.

FIG. 12 is an exemplary diagram illustrating a food container with taglocations.

FIG. 13 is an exemplary block diagram of the components of a food tagcontainer with a tag, and a reader on a network.

FIG. 14 is an exemplary block diagram of the supplier and consumercomponents of a pet feeding system and method.

FIG. 15 is an exemplary block diagram of representative tag dataprogramming components of a pet feeding system and method.

FIG. 16 is an exemplary block diagram showing the food consumption dataanalytics process of a pet feeding system and method.

FIG. 17 is an exemplary block diagram showing the food consumption dataanalytics process of an interrupted pet feeding system and method.

DETAILED DESCRIPTION A. Overview.

Various aspects of specific embodiments are disclosed in the followingdescription and related drawings. Alternate embodiments may be devisedwithout departing from the spirit or the scope of the presentdisclosure. Additionally, well-known elements of exemplary embodimentswill not be described in detail or will be omitted so as not to obscurerelevant details. Further, to facilitate an understanding of thedescription, a discussion of several terms used herein follows.

The word “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any embodiment described herein as“exemplary” is not necessarily to be construed as preferred oradvantageous over other embodiments. Likewise, the term “embodiments” isnot exhaustive and does not require that all embodiments include thediscussed feature, advantage or mode of operation.

The various embodiments of the present invention provides for thewireless communication at least between a food item and a feeding bowl,or between a food item and a smartphone. The communication between theobjects just described incorporating wireless devices, readers, and tagsis well known to those skilled in the art, and comprise a large body ofwork. It is not the intention to limit the types of wireless devices,readers or tags, the non-limiting description of wireless devices,readers, and tags as follows may be used interchangeably without anydifference in meaning or intention.

An example pet feeding system generally includes a container that storesa volume of a consumable product for a pet, a tag attached to thecontainer that stores product data corresponding to the consumableproduct within the container, and a monitor device configured towirelessly communicate with the tag when the tag is near the monitordevice. The monitor device is configured to receive the product datafrom the tag and determine if the consumable product associated with thetag is acceptable for consumption by a pet using the product data. Themonitor device is configured to provide an alert to the user if theconsumable product associated with the tag is identified by the monitordevice as having a consumption problem for the pet.

B. Wireless Devices and Readers.

Wireless communication technologies such as radio-frequencyidentification (RFID) and near field communication (NFC) utilize radiowaves to wirelessly transfer data from a wireless device to a reader ina contactless manner.

There are various types of wireless devices in use today that utilizewireless communications such as RFID and NFC. Examples of wirelessdevices include but are not limited to proximity cards, passive cards,active cards, smart cards (with or without contacts), security cards,identification badges or identification cards, passports, paymentdevices, electronic devices and smartphones.

A reader may be comprised of various types of electronic devices adaptedfor receiving radio signals from wireless devices such as a passivereader or an active reader, wherein an active reader also transmitsradio signals to be received by the wireless device.

C. Tags in Wireless Devices.

The wireless device includes a “tag” (also known as transponder, RFIDtag, RFID Chip, NFC tag, NFC chip) that stores data and wirelesslycommunicates with the reader via radio-frequency electromagnetic fieldsin either a duplex communication manner or a half-duplex communicationmanner. Tags may also be comprised of a read/write configuration thatare programmable by the reader.

A tag is comprised of an integrated circuit and an antenna connected tothe integrated circuit. An active tag includes a battery to provideelectrical power and a passive tag includes a capacitor to store energyreceived from the radio signal of the reader. The tag may be comprisedof various tag technologies.

The integrated circuit in the tag is for storing and processinginformation, modulating and demodulating a radio-frequency (RF) signal,collecting DC power from the reader signal and other functions. Theintegrated circuit includes memory to store various types of data (e.g.pet and owner identification data, product ordering data, logisticsdata, food production data, food portion data). The integrated circuitalso includes either a chip-wired logic or a programmed (orprogrammable) data processor for processing data received and to besent.

The antenna in the tag is for receiving a radio signal from a readerand/or transmitting a radio signal to the reader. With a passive tagtechnology, the antenna also provides electrical power to integratedcircuit without a battery via magnetic induction between the antenna andthe reader located within each other's near field.

FIG. 1 is an exemplary diagram illustrating a devices and functions of afood tag transponder system comprised of a packaged food item 104 towhich a tag is affixed, in this drawing, embedded into a label 105, afood serving bowl 100 into which food 106 from the food container willbe poured. The food serving bowl, bring in communication with a scale101 provides for the accurate and real-time monitoring of the amount offood being poured into the bowl. A tag reader 102 in communication witha processor not shown wirelessly receives certain data from the tag inthe food label 105 relating to the preferred weight of the food serving.Having computed a match between the preferred weight of the food servingand the actual weight as computed by the scale, the processor not shownactivates a visual indicator via one of many means includingilluminating a light 103, and/or providing a message on a wirelessdevice such as a smartphone 107, thereby alerting to the food giver thatthe proper food portion has been entered into the bowl 100.

FIG. 2 is an exemplary diagram illustrating a devices and functions of afood tag transponder system. As a variation to the system and methodjust described, the variation shows a food serving bowl 200 into which afood weighing capability not shown has been integrated, for instance, apressure sensor and transducer, or an analog to digital scale. Asanother variation, a tag reader 102 in communication with a processornot shown wirelessly receives certain data from the tag in the foodlabel 105 relating to the preferred weight of the food serving. Havingcomputed a match between the preferred weight of the food serving andthe actual weight as computed by the scale, the processor not shownactivates an audible indicator via one of many means includingactivating a sound 201, and/or providing an audible message or signal ona wireless device such as a smartphone 107, thereby alerting to the foodgiver that the proper food portion has been entered into the bowl 200.

FIG. 3 is an exemplary illustration of a block diagram of the devicescomprising a food tag system and method. More specifically, a cloud 300database serves as a central server and data center incorporating aplurality of databases, the cloud being a database or plurality ofdatabases residing on various devices including, but not limited to awireless handheld device, a computer, or one or more computers orservers on a network such as the Internet. The use of the term “cloud”is not meant to be limiting, and defines the storage upon, communicationwith, and processing by the various devices and communication interfacesjust mentioned.

Therefore, in the drawing, the cloud 300 is shown in communication witha smartphone 307, the communication link 306 therebetween being wellknown networks such as a cellular network, or a LAN, and a food bowl 309comprising a tag reader in direct or indirect communication with thecloud via well-known means such as through a processor in acommunication format for Bluetooth communication with a wireless devicenot shown, or via a LAN device such as a wireless router on theinternet.

A plurality of data resides in the cloud including, but not beinglimited to a database containing food production data 301, the data atleast including the source of food and/or food ingredients used tomanufacture food, and production information, for example, datacorrelating purchased food ingredients to production lot numbers, dates,and other related information typically recorded by food manufacturers.

Another food container database 302 stores information related toindividual containers into which manufactured food is packaged andassociated with a unique tag ID. ID tag numbers are used throughout theproduct's lifecycle, then retained as archival records.

Another database 303 contains data related to unique animals. Datafields may include one or more of the following: owner's ID, pet weight,pet type, preferred daily portion of food the pet should eat, or anyother information deemed relevant to pet nutrition and pet owners.

It should be noted that a corollary to the database just described wouldbe a database containing only human information such as unique ID, size,weight, daily energy requirement, and other relevant nutritionalinformation.

Another database 304 contains data related to each owner of each uniqueanimal. Data fields may include one or more of the following: owner'sname, address, email address, phone numbers, pet ID, food subscriptionpurchase preferences, payment type preferences, or any other informationdeemed commercially relevant to pet owners.

Other databases may be added to the cloud from time to time, and theconfiguration, data structure or even the necessity of the databasesjust described may change from time to time to support evolvingproduction, sales, customer relationship, or operations models.

An important component of the system and method of one or more of thevarious embodiments is the ability to correlate individual packages offood with food safety monitoring. This requires the ability to updatedata related to each food production lot with information obtained afterthe food is manufactured, packaged and distributed to customers. Suchupdates may include subsequent notice of contamination of a foodingredient from an upstream source.

One source of food safety monitoring information is the US Food and DrugAdministration (FDA) that publishes warnings and food recall notices.Therefore, the drawing shows a perpetual link to the FDA 305 via an API,although the food safety data source is not limited to the FDA, nor tothe necessity of an API. Data may be obtained from other sources, andmay be manually entered into the database as information is obtained.

The system of one or more of the various embodiments further comprises afood measuring means 310 in communication with the food bowl 309, themeasuring means being used to measure the portion of food that will betransferred from a food item with a wireless tag 308, informationrelated to the tag, and the pet ID receiving the food being stored inthe cloud as previously described.

FIG. 4 is an exemplary illustration of a block diagram of a food bowl ona network. In one variation, a food bowl 400 comprises a processor 402in communication with a tag reader 401, a food measuring device such asa scale 301, a memory 403 and a means to communicate with a network 306.Together, the food bowl provides for communicating with a tag of a foodpackage not shown, for determining the desired food portion, and forcommunicating to a person filling the bowl that the desired portion hasbeen filled into the bow.

FIG. 5 is an exemplary illustration of a block diagram of components ofa food container with a tag. More specifically, the simplerepresentation of a food item 104 shows that the item comprises foodcontained within a container structure 500, and that a tag 501 isaffixed to the structure. The methods of affixing a tag to a consumerproduct package are well known to those skilled in the art and includeembedment into the actual structure material, laminating a tag upon alabel that is affixed to the structure, or affixing the tag directly tothe structure surface by an adhesive or similar means.

FIG. 6 is an exemplary diagram illustrating the process flow of a taggedfood item and food bowl on a network. In the drawing, a food bowl with areader 600 has established communication with a tag on a food item 601.The reader 600 communicates the tag data to the processor not shown butincorporated into the feeding bowl system as previously described. Theprocessor validates the tag ID 602 by one or more means such ascomparing the ID to a lookup table contained on the processor's memory,or communicating the ID to the cloud with a validation request. If thetag cannot be validated, communication between the reader and tag isterminated.

If the tag is correctly validated, the tag 603 communicates to thereader, and the reader 605 receives and transmits to the processor, orMCU, certain data related to the food including at least thepredetermined food portion. Upon receiving the tag ID and associateddata, the MCU performs a lookup 606 to determine whether any of the dataparameters transmitted from the tag have been superseded by any datacontained in the cloud. It does this by communicating through variouscommunication links 607, any one of which may be a LAN, WAN, localmemory, or wireless connection to a smartphone that may have downloadedand stored such data, or to subsequently connect to the network via thesmartphone.

In the simplest terms, the lookup of tag data will result in one of twostatuses 609, those being that the data originally programmed into thetag remains unchanged, or that the programmed tag data has beensuperseded. If there is no change, no visual or audible feedback will bepresented to the person filling the bowl, and the person continues tofill the bowl until the “full” alert is activated 614. On the otherhand, if the MCU 610 identifies a newer version of the data, it receivesspecific information from the cloud relating to the version update. Theupdate is made for any number of reasons, including but not limited to afood recall 611, daily feeding portion changes, or that the current dateis outside of the recommended date range during which the food should beconsumed. The date range may have expired prior to the current date, ormay begin at a future date when compared to the current date. These justdescribed reasons for superseding the previously programmed tag data arenot exhaustive, but are merely presented as illustrative examples of thetypes of events that may cause the originally programmed tag data tochange.

If the MCU identifies a changed condition, it processes the change intoan appropriate alert 612. If the alert represents a food recall, thetype of alert may be at least one of the activation of an audible orvisual signal from the food bowl, or a push notification 613 to thesmartphone associated with the tag and/or customer database.

On the other hand, if the changed condition is a change in foodportions, which may not be uncommon for pets that are following a weightloss program, the MCU will simply update the food portion expectationsfor that particular meal, and re-set the scale parameters so that theowner, without knowing that specific food portions have changed,continues to fill the bowl until the “full” alert is activated 614.

FIG. 7 is an exemplary diagram illustrating the process flow of a fooditem with a tag. At the start of any production cycle, food ingredientsare acquired 701 from one or more suppliers. Various data related toeach acquired food component are entered into a database as an inventoryitem that will later be associated with a given production lot 702.Inventory management systems are many, and are well known to thoseskilled in the art. As the production of a new food lot, or batch,commences 705, the batch becomes in-process inventory, and on completionis considered non-packaged finished goods ready for packaging. Thedatabase is correspondingly updated, tracking the ingredients throughoutthe production chain.

Based on an individual customer's order 700, the system of one or moreof the various embodiments allocates the appropriate volume ofin-process food 706 to the customer, and moves the food product to thepackaging line 709 where the food will be packaged. A tag, programmedwith data specific to the customer's food item as previously described,is affixed to the packaged food 710 and the food is shipped to thecustomer. The database is updated with the production data.Coincidentally, the shipping data is updated 711, and the customer'sorder history and planned future shipment information is updated,thereby scheduling the production requirements for future customerorders.

Various food source tracking systems are routinely used by artisans inthe food production industry, and are well known. Since the results fromlengthy food and ingredient quality and safety testing processes areoften obtained after the manufactured food has entered the distributionchannel, it is important to maintain a persistent data connectionbetween a standard food safety data source and the food and ingredientsproduced, packaged and shipped. One data source is the FDA 704 whichroutinely tests food products for safety, the FDA. FDA food safety andrecall data being correlated to the food ingredients, sources andproduction lots provides the trigger to update the originally programmedtag data in the database so that when the tag communicates with thedatabase via the food bowl reader 712, the conflict between theoriginally programmed, and the updated tag data will subsequentlytrigger a food alert as previously described.

D. Subscription Orders as a Method of Driving JIT Production.

The various embodiments of the present invention further teaches a novelmethod of scheduling food production using subscription-based foodsales, and more precisely, buy monitoring and analyzing actual foodconsumption data by each pet owned by each subscribing customer.

In a typical production planning, inventory creation and sales system,food production planning is based generally on historical productiondata, and product sell-through data. The various embodiments of thepresent invention provide for the estimated appropriate daily energyrequirements (in kcal) of each pet for which food is purchased, to drivefuture production planning, packaging and logistics capacity.

More specifically, in one or more of the various embodiments, a customerorder 700 entered into the system of one or more of the variousembodiments contains the precise daily kcal requirements for the petthat will consume the food. The kcal/volume ratio, as well as theprojected future delivery dates of each recurring food subscriptiondelivery, all of which are known by the food manufacturer under one ormore of the various embodiments, establishes the volume of ingredientsand production schedules required to meet the delivery schedules. As thepet's actual consumption changes during the pet's lifetime, the dailyenergy requirements in kcal are modified by a processor not shown, thenewly processed data thereby driving modifications to the productionplanning volumes.

Therefore, if an initial order meeting the production schedule resultsin an inadequate immediate supply of food required to fulfill the order,one of the production parameters 707, a production order for the precisenumber of kcals specified by the order is entered into a productionorder database 708. Thereafter, and at each subscription renewal period,for instance, one calendar week, the future recurring subscriptionrequirements are entered into the production planning database inadvance of the actual production schedule as a means of manufacturingthe food just in time for shipping to the customer under the preferredsubscription purchasing terms.

FIG. 8 is an exemplary diagram illustrating the process flow throughoutthe lifecycle of a tag. The systems, processes and methods of one ormore of the various embodiments provide for a predictable life cycle foreach individual tag. Although many tag manufacturers provide for somelevel of programming of tags before being shipped to commercial tagpurchasers, for clarity, tag data as referred to herein discounts anypre-programmed information, and assumes that tag data includes theinformation minimally required to provide for the communication betweena food item with a tag and a food bowl, and additional datacorresponding to food ingredients, safety updates, portion changes, andother types of data previously described.

A tag is acquired from a tag manufacturer 800, the tag being either araw, un-programmed IC package 801, already embedded within a foodcontainer 802, or embedded into a generic, printable label 803. Thethree tag configurations are not exhaustive, but merely serve as threeexamples of the many configurations of tags as may be preferred by themany manufacturers.

As is typical in a manufacturing environment, purchased good are addedto an inventory database 802 for later use in production. As thecustomer order drives the JIT production requirement 806, a tagpreviously entered into inventory is pulled, decrementing the totalinventory count in the database 807. The tag will be programmed withdata specific to the customer and food item 808, the types of such databeing previously described. The tag then accompanies the food itemthrough a logistics/shipping process until it reaches the ultimateconsumer. Upon use by the consumer, the tag, in indirect communicationwith the cloud 810 begins a food consumption monitoring process 811 thatcontinues until the food is consumed.

E. Monitoring the Totality of a Food Production.

This novel process, for the first time, provides for the database toretrieve daily dispensing of a food portion, analyze each food portionagainst the estimated food portion, and decrement the retrieved volumeof food poured from the container from the total volume originallydelivered in the container. This process allows the database to identifywhen the entire food container is emptied of food.

On the other hand, if as an illustrative example, the FDA issues a foodrecall for an ingredient incorporated into the food lot from this thecontainer was filled, at the immediate instant of the issuance of thefood recall, one or more of the various embodiments provides for thelocating of every effected food package, and more importantly, providesimmediate data related to the actual remaining volume of effected foodthat has not been consumed.

This process just described represents an entirely novel method of usinga tag to track individual food products from upstream component sourcingby a food manufacturer, to ultimate consumption by pet dogs and cats.

Upon the computed exhaustion of the food contained within a container,the tag data associated with the food lot and customer is archived 812and removed from the active system.

On the other hand, if a change is made to the tag data, for instance, arecall notice published by the FDA as previously described, theestimated food consumption rates, the percent of any given food lot thathas been consumed, and the volume of food from any given productionbatch or lot can be instantly determined in real time, thereby providingthe food supplier the ability to take appropriate action as a means tomitigate potential animal health issues or death, to retrieve food notyet consumed, to precisely enumerate the volume of food remaining in themarketplace, and to know with precision when the marketplace has beenpurged of all recalled food.

FIG. 9 is an exemplary diagram illustrating the process of alerting apet owner. In the drawing, a pet owner prepares to feed the pet bymoving the food container with tag in proximity of the food bowl andreader 900 to facilitate the food transfer from container to bowl. Thetag and reader being in communication 901 begin transferringauthentication and food data. As previously described, the readerindirectly transmits the tag data to the cloud 902 for comparison to theoriginally programmed tag data.

If the actual tag data, or any components of the data, differ from thecloud data corresponding to the tag ID, the tag data will be deemed tohave been updated.

Therefore, if the tag data and cloud data for the same tag are equal,the owner simply continues filling the bowl as planned 904 until thebowl MCU 905 determines that the poured-in food volume equals theexpected volume 906. When equal conditions exist between expected andactual food volume occurs, the food pourer will be alerted by variousvisual and/or audible means 907 that the right food portion has beenadded to the bowl. The pourer stops pouring.

On the other hand, if the analysis of the tag data compared to thecorresponding data on the cloud for that tag is not equal, the systemprovides for a lookup of each data field 908 as a means to determinewhat data fields have been updated. In the drawing, the illustrativeexample shows that the data mismatch between the programmed tag data andthe current tag data on the cloud is a result of a food recall thataffects this package of pet food. The food bowls MCU's determination ofa food recall causes an alert signal 909 to be transmitted to thesmartphone or wireless device associated with the particular food item,and triggers the activation of audible and/or visual alert indicators910 proximate to the feeding bowl. In this case, catastrophe has beenavoided since the pet owner does not feed this food to the pet 911.

However, the mismatch in data between the originally programmed tag andthe corresponding data fields on the cloud may be the result of aportion adjustment to the pet's daily feeding regimen 912. The system ofone or more of the various embodiments provides for the modified portiondata to be communicated 913 to the bowl MCU, thereby adjusting theexpected food weight 914 to equal the weight of the new portion.

Not knowing that any mismatch between the tag and the cloud dataoccurred, the pourer simply continues filling the bowl as planned 904until the bowl MCU 905 determines that the poured-in food volume equalsthe updated expected volume 906. When equal conditions exist betweenexpected and actual food volume occurs, the food pourer will be alertedby various visual and/or audible means 907 that the right food portionhas been added to the bowl. The pourer stops pouring.

FIG. 10 is an exemplary diagram illustrating the process of alerting apet owner. In some instances it may be preferable to tag pet foodsupplements or medicaments as a means of maintaining a knowledge base oflocation, amount consumed and amount remaining at any given time. Forinstance, medicaments may be recalled after the veterinarian prescribesthe medicament, and even after which time the pet owner beginsadministering the medicament.

In the drawing, a producer provides production data 1004 of themedicament into a production database 1002, the data comprising lablocation, ingredient sources, processes, batch or lot information, orother data as preferred, not dissimilar to the food production datapreviously described.

In a traditional manner, the medicament supplier distributes themedicament to a pharmacy or veterinarian 1005 which then fills aprescription and, at the same time, programs the tag with patientinformation including the patient's email address and mobile phonenumber 1006, 1007.

Thereafter, the patient, typically the pet's owner, receivescommunication from the cloud recommending to download and install amobile application 1009 that will allow push alerts to be sent to thepatient's phone. If the patient's ID is associated with a food bowl withtag reader, any push notifications related to the medicament would alsobe pushed to the food bowl MCU.

If at any time the FDA or other safety monitoring data source 1003, thedata from which is integrated into the cloud database, issues an alert,warning or recall for the medicament in the patient's possession, afterthe patient installs the wireless device app, the cloud servers willpush the alert notification to the patient, thereby preventing thepatient from administering the medicament 1010.

In the event that a push notification is not sent to the patient's app,anytime that the phone with integrated reader, or a reader enabled foodbowl is proximate to the tag, the tag will trigger the app to query thedatabase 1011 for safety or other medicament related updates. Thedatabase will respond to queries 1013 by sending responsive informationto the patient's wireless device app, causing the patient to followingthe appropriate instructions.

FIG. 11A is an exemplary diagram illustrating one variation of a foodcontainer 1100, the food container comprising a box-like structure witha twist-off or pull-off re-closable cover. The container may have a tagembedded into the cover or material at the time the cover or materialare manufactured, or may have a tag that was affixed directly, orindirectly, by means of a label affixed to the structure at the timefood was introduced to the container during the manufacturing process.

FIG. 11B is an exemplary diagram illustrating another variation of afood container 1101, the food container comprising a box-like structurefrequently used as a milk carton with a peel-open, re-closable pouringspout. The container may have a tag embedded into the structure at thetime the structure or material used in the structure was manufactured,or may have a tag that was affixed directly, or indirectly, by means ofa label affixed to the structure at the time food was introduced to thecontainer during the manufacturing process.

FIG. 11C is an exemplary diagram illustrating another variation of afood container 1102, the food container comprising a jar-like structurefrequently used for medicaments or nutritional supplements with atwist-open, re-closable pouring cover. The container may have a tagembedded into the cover or structure at the time the cover or structurewas manufactured, or may have a tag that was affixed directly, orindirectly, by means of a label affixed to the structure at the timefood was introduced to the container during the manufacturing process.

FIG. 11D is an exemplary diagram illustrating another variation of afood container 1103, the food container comprising a metallic canstructure frequently used wet pet foods with a pop-open top, or a sealedtop openable by use of a typical can opener. The metal container mayhave a tag that was affixed directly, or indirectly, by means of a labelaffixed to the structure at the time food was introduced to thecontainer during the manufacturing process.

FIG. 11E is an exemplary diagram illustrating another variation of afood container 1104, the food container comprising a bag-like structurefrequently used for dry pet foods with a tear open top. A variation of abag-like structure may incorporate a zip-lock feature allowing for easyre-opening and re-closing of the bag after opening. The container mayhave a tag embedded into the structure material at the time it wasmanufactured, or may have a tag that was affixed directly, orindirectly, by means of a label affixed to the structure at the timefood was introduced to the container during the manufacturing process.

FIG. 11F is an exemplary diagram illustrating another variation of afood container 1105, the food container comprising a rigid lowerstructure and a cellophane type upper structure as may be frequentlyused as a traditional supermarket package for meats. A label 1006 istypically applied to the container after affixing the cellophane topstructure to and about the rigid bottom structure, the labelincorporating a tag that was programmed and affixed to the structure atthe time of manufacturing.

FIG. 11G is an exemplary diagram illustrating another variation of afood container 1107, the food container, frequently referred to as ahybrid package, comprises a thermoplastic lower structure to which anupper metal retaining rim and pop-open cover has been affixed. Thecontainer may have a tag that was affixed directly, or indirectly, bymeans of a label affixed to the structure at the time food wasintroduced to the container during the manufacturing process.

The food, supplement and medicament containers just described are notintended to be exhaustive, and articulating the methods of affixing atag to the many hundreds of foil, tear-open, vacuum-formed, and othertypes of containers would be burdensome. Nevertheless, doing so wouldshow that the tag of one or more of the various embodiments may beaffixed to any type of container into which pet food, nutritionalsupplements or medicaments may be packaged.

FIG. 12 is an exemplary diagram illustrating a food container with taglocations. More specifically, a typical dry food bag 1200 as describedin FIG. 11E is shown with a tag 1202 that was embedded in the structurematerial at the time the material was manufactured, an alternatelocation of a tag 1201 that may have been affixed to the bag at the timeit was sealed, and yet another location of a tag that was incorporatedinto a label 1200 and affixed to the bag during the food packagingcycle. Only one tag would be required to meet the minimum specificationsof one or more of the various embodiments, but alternate locations andmethod of affixing the tags are shown merely for comparative purposes.

The tag is preferably programmed with certain information that may, ormay not appear in human readable form on the label, the informationbeing one or more of the data fields: customer name, pet's name, theduration of time for which the volume of food is intended to last at thedaily food portion amount, daily food portion represented in variousunits, total container volume expressed in various units, productionfacility data, and other data as may be required by regulatory agencies.The data fields just described are not meant to be limiting.

FIG. 13 is an exemplary block diagram of the components of a food tagcontainer with a tag, and a reader on a network.

In the drawing a food manufacturer programs a tag 1300, and theassociated programming data being stored with corresponding alertinstructions in a central database 1301. The database communicates witha feeding device 1305 by means of a network, the network preferablycomprising a cellular network to which a phone 1302 is in communication,and a forward communication from the phone being provided wirelessly1303 to the feeding device. One alternate network may provide for thecommunication between a database and feeding device via the internet viaWIFI 1304 using well known devices and interoperable communicationsprotocols.

The feeding device 1305 preferably comprises a food scale, a tag reader,a processor and memory, a wireless transponder, and an audible and/orvisual indicator. A tag 1036 affixed to a food item contains daterelated to the food and customer, the data being transferable betweenthe tag of the food item and the reader of the feeding device.

FIG. 14 is an exemplary block diagram of the supplier and consumercomponents of a pet feeding system and method.

F. Food Manufacturing Operations.

In one or more of the various embodiments, the entirety of foodproduction is a JIT-demand-driven under a model that incorporates foodpurchasing subscriptions, for instance, weekly production and deliveryto each customer, with precise real-time knowledge of how many calorieseach pet customer will consume each day between subscription deliveries.

A central database, or a network of federated databases 1400 store andprocess a plurality of operationally integrated, or operationallycompartmentalized databases, the databases comprising for example, butnot limited to, unique customer records, unique pet records, pet foodand food portion records, production history and production planningrecords, and food component source and safety data. The food and tightlycorrelated customer and pet databases are preferably in communicationwith supplier operations management software and databases, directly orvia middleware.

Those skilled in the art of food production planning and productionmanagement will immediately appreciate that the predictive productionrequirements provided for by one or more of the various embodiments, forthe first time, allow food production planners to base production on ajust in time process rather than the outdated “plan based on historicalmodels, evaluation of current sales commitments, and a variableestimate” to ensure production that is adequate to meet demand.

Therefore, critically important and previously unavailable data such asreal-time actual food consumption can be integrated into overall foodsupplier operations 1401 thereby increasing predictive accuracy,efficiencies that translate to cost savings and preservation oroperating cash, sales, production planning, and highly important, directmanufacturer-to-consumer relationship management that drives brandpreference and goodwill.

G. System and Method to Increase Customer Loyalty and Retention.

The individualized pet food production of one or more of the variousembodiments provides the consumer 1402 with an unprecedented level ofnutritional awareness and food safety confidence. The system and methodof one or more of the various embodiments incorporates a unique tag IDassociated with the consumer's purchased food item 1403, the tag beingin communication with a feeding system that updates food informationwith each subscription delivery 1404 and with each daily feeding 1405,the communication continuing between the food item tag and reader 1406feeding device until the food in the container is exhausted 1407.

The system and method of one or more of the various embodimentstherefore delivers to the consumer the assurance of immediate alertswhen safety issues arise with their pet's food, assurance that they willcontinue to be delivered the freshest possible pet food on a preferreddelivery schedule, and assurance that they are feeding their pet theprecise number of calories that have been determined as the optimumdaily portion for their pet.

No other pet food production and food tracking system has everapproached, not have any anticipated the functionality of one or more ofthe various embodiments.

FIG. 15 is an exemplary block diagram of representative tag dataprogramming components of a pet feeding system and method.

Coding schemes, protocols and data string lengths for tags vary widely.Therefore, rather than providing a precise coding scheme, the drawingshows a representative example of how certain pet production data may beincorporated into a data string.

The data 1500 embedded into a tag for a food item preferablyincorporates at least the minimum information as required byregulations, and a unique pet food item identifier, and data related toa unique pet owner or pet that will consume the unique food item.

Nevertheless, other pet, food, production, date and time, reorder orother data may be additionally programmed into the tag at the time ofmanufacture.

FIG. 16 is an exemplary block diagram showing the food consumption dataanalytics process of a pet feeding system and method.

An embodiment provides for the real time data collection associated witheach food item sent to each customer, and further continually analyzes1600 the data for potential food safety issues that arise after the foodis delivered to the customer. Further, one or more of the variousembodiments provides for the perpetual data collection and analysis 1601of real time food consumption rates related to each food item, andconsolidates all data from all food items produced from each foodproduction batch to determine the volume or percent of the food batchthat has been consumed, and the total non-consumed food remaining in theconsumer marketplace.

Real time and scheduled data exchange therefore 1062 therefore continuesbetween a customer's pet food bowl and the food producer's centraldatabase.

A normal record 1603 in the database for a given customer may illustratethe actual and predicted daily food portion fed to the pet, and arunning tabulation of the total consumed and unconsumed portion of thefood in a unique container.

FIG. 17 is an exemplary block diagram showing the food consumption dataanalytics process of an interrupted pet feeding system and method.

An embodiment provides for the real time data collection associated witheach food item sent to each customer, and further continually analyzes1700 the data for potential food safety issues that arise after the foodis delivered to the customer. Further, one or more of the variousembodiments provides for the perpetual data collection and analysis 1701of real time food consumption rates related to each food item, andconsolidates all data from all food items produced from each foodproduction batch to determine the volume or percent of the food batchthat has been consumed, and the total non-consumed food remaining in theconsumer marketplace.

Real-time and scheduled data exchange 1702 therefore continues between acustomer's pet food bowl and the food producer's central database.

In the instance that the individual food item is subject to a foodrecall 1703, the means to alert the customer as previously described areactivated, and the customer immediately ceases feeding the pet the foodfrom the recalled food item.

Further, the recall triggers the automated priority re-order of areplacement food item 1704 meeting the same customized parameters ofeach recalled food item, replacing the recalled food items withnutritionally similar replacements.

New tags will be programmed for and affixed to each replacement fooditem preferably following the processes previously described, with theeffective USE date of the replacement item beginning on the date ofarrival of the food item at the customer's location.

It should be noted that the subscription period may or may not changebased on the delivery of a full food item replacement, and the paymentperiod associated with each subscription delivery may or may not change,the decisions being business-based at the preference of the foodsupplier.

The drawing shows a representative data record 1705 illustrating aninterruption in the feeding schedule of the pet on Day 5, Day 5 beingthe day that the food recall was issued and the priority overnightdelivery of the replacement food activated. The daily food tracking ofthe replacement food resumed on the delivery day, in the example, Day 6.

As a means to mitigate residual risk and liability, the manufacturer,possessing the data related to all recalled food that was not consumedat the time of the consumer alert, may communicate directly with theowner to ensure that the owner follows the recommended protocol, forinstance, verifying that the remaining volume of the recalled food wasdestroyed, or returned to a facility at the producer's direction.

Although specific embodiments have been illustrated and describedherein, it will be appreciated by those of ordinary skill in the artthat a wide variety of alternate and/or equivalent implementations maybe substituted for the specific embodiments shown and described withoutdeparting from the scope of the present disclosure. This application isintended to cover any adaptations or variations of the embodimentsdiscussed herein.

At least one embodiment of the pet feeding system is described abovewith reference to block and flow diagrams of systems, methods,apparatuses, and/or computer program products according to exampleembodiments of the invention. It will be understood that one or moreblocks of the block diagrams and flow diagrams, and combinations ofblocks in the block diagrams and flow diagrams, respectively, can beimplemented by computer-executable program instructions. Likewise, someblocks of the block diagrams and flow diagrams may not necessarily needto be performed in the order presented, or may not necessarily need tobe performed at all, according to some embodiments of the invention.These computer-executable program instructions may be loaded onto ageneral-purpose computer, a special-purpose computer, a processor, orother programmable data processing apparatus to produce a particularmachine, such that the instructions that execute on the computer,processor, or other programmable data processing apparatus create meansfor implementing one or more functions specified in the flow diagramblock or blocks. These computer program instructions may also be storedin a computer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meansthat implement one or more functions specified in the flow diagram blockor blocks. As an example, embodiments of the invention may provide for acomputer program product, comprising a computer usable medium having acomputer-readable program code or program instructions embodied therein,the computer-readable program code adapted to be executed to implementone or more functions specified in the flow diagram block or blocks. Thecomputer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational elements or steps to be performed on the computer or otherprogrammable apparatus to produce a computer-implemented process suchthat the instructions that execute on the computer or other programmableapparatus provide elements or steps for implementing the functionsspecified in the flow diagram block or blocks. Accordingly, blocks ofthe block diagrams and flow diagrams support combinations of means forperforming the specified functions, combinations of elements or stepsfor performing the specified functions, and program instruction meansfor performing the specified functions. It will also be understood thateach block of the block diagrams and flow diagrams, and combinations ofblocks in the block diagrams and flow diagrams, can be implemented byspecial-purpose, hardware-based computer systems that perform thespecified functions, elements or steps, or combinations ofspecial-purpose hardware and computer instructions.

The present invention may be embodied in other specific forms withoutdeparting from the spirit or essential attributes thereof, and it istherefore desired that the present embodiment be considered in allrespects as illustrative and not restrictive. Many modifications andother embodiments of the pet feeding system will come to mind to oneskilled in the art to which this invention pertains and having thebenefit of the teachings presented in the foregoing description and theassociated drawings. Therefore, it is to be understood that theinvention is not to be limited to the specific embodiments disclosed andthat modifications and other embodiments are intended to be includedwithin the scope of the appended claims. Although methods and materialssimilar to or equivalent to those described herein can be used in thepractice or testing of the pet feeding system, suitable methods andmaterials are described above. Thus, the pet feeding system is notintended to be limited to the embodiments shown, but is to be accordedthe widest scope consistent with the principles and features disclosedherein.

What is claimed is:
 1. A pet feeding system, comprising: a containerthat stores a volume of a consumable product for a pet, wherein thecontainer is configured to allow a user to selectively dispense theconsumable product for consumption by a pet; a tag attached to thecontainer, wherein the tag stores product data corresponding to theconsumable product within the container; and a monitor device configuredto wirelessly communicate with the tag when the tag is near the monitordevice; wherein the monitor device is configured to receive the productdata from the tag and determine if the consumable product associatedwith the tag is acceptable for consumption by a pet based on the productdata; wherein the monitor device is configured to provide an alert tothe user if the consumable product associated with the tag is identifiedby the monitor device as having a consumption problem for the pet. 2.The pet feeding system of claim 1, wherein the tag is comprised of anRFID tag, NFC tag or a transponder.
 3. The pet feeding system of claim1, wherein the monitor device is comprised of a mobile phone.
 4. The petfeeding system of claim 1, wherein the monitor device is comprised of afood bowl adapted for receiving the consumable product.
 5. The petfeeding system of claim 1, wherein the monitor device is comprised of areader.
 6. The pet feeding system of claim 1, wherein the monitor deviceis configured to communicate with a server via a global computer networkto identify potential consumption problems with the consumable productassociated with the tag using the product data.
 7. The pet feedingsystem of claim 1, wherein the product data includes an expiration datefor the consumable product in the container.
 8. The pet feeding systemof claim 7, wherein the monitor device is configured to provide thealert to the user if the current date is after the expiration date forthe consumable product in the container.
 9. The pet feeding system ofclaim 1, wherein the monitor device is configured to acquire anexpiration date from a server for the consumable product in thecontainer, and wherein the monitor device is configured to provide thealert to the user if the current date is after the expiration date forthe consumable product in the container.
 10. The pet feeding system ofclaim 1, wherein the monitor device is configured to determine if theconsumable product in the container is subject to a recall notice. 11.The pet feeding system of claim 1, wherein the monitor device isconfigured to provide safety instructions to the user when a consumptionproblem is identified.
 12. The pet feeding system of claim 1, whereinthe consumable product is comprised of food or medicine consumable bythe pet.
 13. The pet feeding system of claim 1, wherein the product datastored on the tag includes pet identification data identifying the petthe consumable product is to be consumed by.
 14. The pet feeding systemof claim 13, wherein the monitor device transmits the alert to the userif the pet identification data received from the tag does not correspondto the pet.
 15. The pet feeding system of claim 1, wherein the productdata stored on the tag includes portion data corresponding to the pet,wherein the portion data corresponds to an amount of consumable productto provide to the pet for consumption, wherein the monitor device iscomprised of a food bowl with a reader and a scale, and wherein themonitor device is configured to notify the user if too much consumableproduct is placed into the food bowl based on the portion data.
 16. Thepet feeding system of claim 15, wherein the monitor device is configuredto receive updated portion data for the pet, wherein the updated portiondata provides a different amount of consumable product to provide to thepet for consumption compared to the portion data.
 17. The pet feedingsystem of claim 16, wherein the updated portion data is based on theactivity level of the pet or a weight of the pet.
 18. The pet feedingsystem of claim 1, wherein the monitor device is comprised of a foodbowl with a reader and a scale, wherein the monitor device communicateswith a server to determine an updated amount of consumable product toprovide to the pet based on changed pet characteristics, and wherein themonitor device is configured to notify the user if too much consumableproduct is placed into the food bowl.
 19. The pet feeding system ofclaim 1, wherein the monitor device is configured to acquire warningsand recall notices from a server issued by the Food and DrugAdministration, and wherein the monitor device is configured to providethe alert to the user if the consumable product is subject to a warningor recall notice issued by the Food and Drug Administration.
 20. A petfeeding system, comprising: a container that stores a volume of aconsumable product for a pet, wherein the container is configured toallow a user to selectively dispense the consumable product forconsumption by a pet; a tag attached to the container, wherein the tagstores product data corresponding to the consumable product within thecontainer, wherein the product data includes an expiration date for theconsumable product in the container and pet identification dataidentifying the pet the consumable product is to be consumed by, andwherein the tag is comprised of an RFID tag, NFC tag or a transponder;and a monitor device configured to wirelessly communicate with the tagwhen the tag is near the monitor device; wherein the monitor device isconfigured to receive the product data from the tag and determine if theconsumable product associated with the tag is acceptable for consumptionby a pet based on the product data; wherein the monitor device isconfigured to provide an alert to the user if the consumable productassociated with the tag is identified by the monitor device as having aconsumption problem for the pet; wherein the monitor device is comprisedof a food bowl adapted for receiving the consumable product, wherein themonitor device includes a reader configured for communicating wirelesslywith the tag; wherein the monitor device is configured to communicatewith a server via a global computer network to identify potentialconsumption problems with the consumable product associated with the tagusing the product data; wherein the product data stored on the tagincludes portion data corresponding to the pet, wherein the portion datacorresponds to an amount of consumable product to provide to the pet forconsumption, wherein the monitor device is comprised of a food bowl witha reader and a scale, and wherein the monitor device is configured tonotify the user if too much consumable product is placed into the foodbowl based on the portion data; wherein the monitor device is configuredto receive updated portion data for the pet, wherein the updated portiondata provides a different amount of consumable product to provide to thepet for consumption compared to the portion data, and wherein theupdated portion data is based on the activity level of the pet or aweight of the pet; wherein the monitor device is configured to acquirewarnings and recall notices from a server issued by the Food and DrugAdministration, and wherein the monitor device is configured to providethe alert to the user if the consumable product is subject to a warningor recall notice issued by the Food and Drug Administration.